FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource NamingSystem/FHIR Server from package hl7.terminology#current (32 ms)

Package hl7.terminology
Type NamingSystem
Id Id
FHIR Version R5
Source http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/NamingSystem-uri.html
Url http://terminology.hl7.org/NamingSystem/uri
Version 1.0.0
Status active
Date 2022-02-07T00:00:00-00:00
Name URI
Title Uniform Resource Identifier (URI)
Experimental False
Realm uv
Authority hl7
Description As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid: Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR. This OID may also be used in CD.codeSystem.
Kind identifier

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: NamingSystem uri

Summary

Defining URLhttp://terminology.hl7.org/NamingSystem/uri
Version1.0.0
NameURI
TitleUniform Resource Identifier (URI)
Statusactive
Definition

As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt

This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid:

Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.

This OID may also be used in CD.codeSystem.

Identifiers

TypeValuePreferred
OID2.16.840.1.113883.4.873true
URIurn:ietf:rfc:3986true

Source

{
  "resourceType" : "NamingSystem",
  "id" : "uri",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: NamingSystem uri</b></p><a name=\"uri\"> </a><a name=\"hcuri\"> </a><a name=\"uri-en-US\"> </a><h3>Summary</h3><table class=\"grid\"><tr><td>Defining URL</td><td>http://terminology.hl7.org/NamingSystem/uri</td></tr><tr><td>Version</td><td>1.0.0</td></tr><tr><td>Name</td><td>URI</td></tr><tr><td>Title</td><td>Uniform Resource Identifier (URI)</td></tr><tr><td>Status</td><td>active</td></tr><tr><td>Definition</td><td><div><p>As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt</p>\n<p>This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid:</p>\n<p>Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.</p>\n<p>This OID may also be used in CD.codeSystem.</p>\n</div></td></tr></table><h3>Identifiers</h3><table class=\"grid\"><tr><td><b>Type</b></td><td><b>Value</b></td><td><b>Preferred</b></td></tr><tr><td>OID</td><td>2.16.840.1.113883.4.873</td><td>true</td></tr><tr><td>URI</td><td>urn:ietf:rfc:3986</td><td>true</td></tr></table></div>"
  },
  "url" : "http://terminology.hl7.org/NamingSystem/uri",
  "version" : "1.0.0",
  "name" : "URI",
  "title" : "Uniform Resource Identifier (URI)",
  "status" : "active",
  "kind" : "identifier",
  "date" : "2022-02-07T00:00:00-00:00",
  "description" : "As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt \r\n\r\nThis oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid: \r\n\r\nNote that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.\r\n\r\nThis OID may also be used in CD.codeSystem.",
  "uniqueId" : [
    {
      "type" : "oid",
      "value" : "2.16.840.1.113883.4.873",
      "preferred" : true
    },
    {
      "type" : "uri",
      "value" : "urn:ietf:rfc:3986",
      "preferred" : true
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.